Skip to content

Move validate resume step after checkout#11533

Merged
BDevParity merged 1 commit intostable2603from
fix/move-validate-resume-after-checkout
Mar 27, 2026
Merged

Move validate resume step after checkout#11533
BDevParity merged 1 commit intostable2603from
fix/move-validate-resume-after-checkout

Conversation

@BDevParity
Copy link
Copy Markdown
Contributor

Summary

Test plan

  • Resume the publish crates workflow from the release org after this is merged and synced

@BDevParity BDevParity requested review from a team as code owners March 27, 2026 14:56
@BDevParity BDevParity added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Mar 27, 2026
@BDevParity BDevParity enabled auto-merge (squash) March 27, 2026 15:00
@github-actions
Copy link
Copy Markdown
Contributor

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

  • Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
  • Should be a legit fix for some bug, not adding tons of new features.
  • Must either be already audited or not need an audit.
Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

@paritytech-review-bot paritytech-review-bot Bot requested a review from a team March 27, 2026 15:01
@BDevParity BDevParity merged commit 8380d3f into stable2603 Mar 27, 2026
224 of 230 checks passed
@BDevParity BDevParity deleted the fix/move-validate-resume-after-checkout branch March 27, 2026 15:43
EgorPopelyaev pushed a commit that referenced this pull request Mar 31, 2026
## Summary
- Moves the "Validate resume preconditions" step after the "Checkout
stable branch" step so `git ls-remote` runs in an initialized git repo
- Fixes the failed publish crates workflow resume:
https://github.com/paritytech-release/polkadot-sdk/actions/runs/23620337279/job/68797902086#step:25:20

## Test plan
- Resume the publish crates workflow from the release org after this is
merged and synced
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

R0-no-crate-publish-required The change does not require any crates to be re-published.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants